Update 'RetrieveFullPathForCollection' to return correct paths #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A thought - is LINQ performant enough here? |
Microsoft does put a lot of work into keeping LINQ performant as it's really popular, and we do use it throughout the code If you're worried though, there's this repo benchmarking LINQ, and if you want to test this query in particular, you could use BenchMarkDotNet to test |
|
I think it should be alright, but I'll read into those when I get the chance - they'll be good to know! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #48
This PR fixes a minor bug where
CollectionRetrieval.RetrieveFullPathForCollectionwasn't including slashes between slugs in the generated path.